Intends to use the Graph Tally Collector contract in the test infra RAV generation.

🔍 TAP V2 Receipt Processing Investigation

✅ RESOLVED ISSUES

EIP-712 Domain Mismatch ✅ FIXED

• Gateway Configuration: Fixed to use GraphTallyCollector instead of TAPVerifier
• Test Code: Fixed both Stage 1 and Stage 2 to use GRAPH_TALLY_COLLECTOR_CONTRACT
• Verification: All receipts now created with matching domain
  0xB0D4afd8879eD9F52b28595d31B441D079B2Ca07

🚨 ROOT ISSUE IDENTIFIED: Gateway → Indexer-Service Communication Break

Current Symptoms

📈 New metric: sender="0xf39Fd6e51aad88F6F4ce6aB8827279cfffb92266" =
100000000000000000000
📈 New metric: allocation="0x378015Dd02ceae3C7506A3372c66C614112a2Ff1",sender="0xf39Fd
6e51aad88F6F4ce6aB8827279cfffb92266" = 0
After V2 batch 8: RAVs created: 0, Unaggregated fees: 0 (0.0% of trigger threshold)

Database Reality Check

-- Both tables empty despite 240+ successful V2 queries
SELECT COUNT() FROM tap_horizon_receipts; -- 0 rows
SELECT COUNT() FROM scalar_tap_receipts; -- 0 rows

Analysis

• ✅ Test → Gateway: 240+ V2 queries successfully sent to gateway (HTTP 200)
• ✅ EIP-712 Domains: Perfect match between test and gateway configuration
• ✅ Database Schema: All tables exist and accessible
• ❌ Gateway → Indexer-Service: No receipts reaching database at all

🎯 NEXT INVESTIGATION STEPS

The issue is in the Gateway → Indexer-Service → Database pipeline. Since receipts
aren't being stored, we need to examine:

1. Gateway Receipt Processing: Does gateway actually create and forward receipts to
   indexer-service?
2. Indexer-Service TAP Middleware: Is it configured to accept and process V2 receipts?
3. Network Communication: Are requests actually reaching indexer-service from gateway?

🔍 DETAILED FINDINGS

What's Working

• Test generates valid V2 receipts with proper protobuf encoding
• Gateway accepts requests and returns HTTP 200
• Database has complete V2 schema including tap_horizon_receipts
• Services are Horizon-enabled and configured correctly
• EIP-712 domains match exactly: 0xB0D4afd8879eD9F52b28595d31B441D079B2Ca07

What's Broken

• Zero receipts in database after 240+ successful queries
• Gateway appears to accept receipts but doesn't forward them
• TAP Agent metrics show sender total but allocation-specific fees remain 0

Key Insight

The "sender total = 100 GRT" but "allocation fees = 0" pattern suggests:

• Some receipt processing is happening (sender metrics updated)
• But receipts aren't properly attributed to the collection/allocation
• OR receipts aren't being stored in database at all

This points to either:

1. Gateway not forwarding V2 receipts to indexer-service
2. Indexer-service rejecting V2 receipts (validation failure)
3. ...?

The investigation should continue with examining gateway logs and indexer-service
configuration to trace the exact point of failure in the receipt processing pipeline.

Signed off by Joseph Livesey [email protected]